Hello, we've got a Problem with the "configmgr remote control driver" from SCCM. If we install the SCCM Client, on some Hosts the display will not work after a reboot. I can remember we had the same problem for about one year, but then with the SMS 2003. If we deleted the "sms mirror driver" the problem was solved. But if we want to delete the "configmgr remote control driver", it doesn't work; The display will be dark. To fix that problem, we booted in VGA - Mode and made a system recovery. The remote tools are disabled in client configuration. Has anyone of you an Idea to fix it? Thanks a lot! Michael

Hi all , I am also sharing the same issue on some pc's that are equiped with the latest Nvidia video card drivers. I believe it is some incompatibillity with the video card driver or bus where it resides in . Kenny

hacky1872 wrote: Hi all, i have solved the problem, but over an indirection ;-) If you have got a packet assembling software (e.g. FlexNet AdminStudio), you can deactivate the Feature "SMSRemoteTools", and it will not install the configmgr remote control driver on the target computer. Why don't you just remove the role instead of hacking it? removing the role removes the driver too.

What you need to do is what I suggested - open a case with customer support so that they can check and see if there is an issue that needs to be addressed.

Hi, I had the same problem and solved it byI disabling the SMSRemote control agent in SCCM andinstalling the latest video card driver before the SCCM agent. (I did it with nVidia 6200) Zolee

Hi All,I'm an Escalation Manager at Microsoft. We've been trying to find root cause of this issue but haven't been able to create an in-house repro which is needed for the repeated debugging that we need to do. In order to facilitate finding root cause of this issue I'm willing to provide a FREE SUPPORT CASE to the first two people who can repro this issue who send me email. To qualify for the free case I'd ask that you please meet the following criteria:1. Can repro this issue at will2. Willing to work with our engineers in a timely manner to get any information they require to get to root cause including providing system images, full dumps, complete hardware specs, etc.3.In the unlikely event that we can't get our hands on the exact hardware needed to repro this, that you would be willing to send a machine to us that it can be repro'd on. Thsi would be done at Microsoft's expense and would be sent back once we are done debugging.I cannot guaranty that we will be able to provide a hotfix or other resolution. The issue may be rooted in third party code or may be related to some base architecture that can't be changed in the short term. However, I have a high level of confidence that we will be able to get to root cause.If you meet the criteria above, please email me directly at khoffman@microsoft.com. Once we have identified two people who can work with us on this, I'll respond back to this thread.Thanks in advance for your help.Keith

Keith - we are experiencing this same problem right now. It started occuring over the past two weeks and only affects NVidia Cards. We have reproduced the problem by removing SMS and then reinstalling SMS and watching the NVidia driver changed to "device cannot start".